Portal: Implementation of new history network #3427
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kdeme
force-pushed
the
finalized-history-network
branch
3 times, most recently
from
500d195 to
1a3cc5a
Compare
|
Specs PR now: ethereum/portal-network-specs#410 |
kdeme
force-pushed
the
finalized-history-network
branch
6 times, most recently
from
8b3ee9b to
d9112d9
Compare
kdeme
force-pushed
the
finalized-history-network
branch
from
d9112d9 to
7e9f420
Compare
This is the type defined/referred to in the specifications
Also bump portal-spec-tests repo for new test vectors
kdeme
force-pushed
the
finalized-history-network
branch
from
b4c177c to
a06f1a3
Compare
kdeme
changed the title
|
Still open items will be handled in other PR as they are related to integration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP, but starting to implement https://ethresear.ch/t/using-portal-network-protocol-for-history-expiry/22658
TODO (not necessarily all in this PR):
Might require ContentDb change due to same content id for BlockBody and Receipts. Unless specs changeSpecs changed so thatContentDbchange is no longer required. See 2b5cebc